fix(settings): show resolved model in Local CLI tests - #6183

Why

When I selected a rolling Claude Code alias such as opus in Settings and clicked Test, Open Design only reported that Claude Code replied successfully. That proved connectivity, but not which concrete model actually handled the request.

Claude Code already includes the concrete model in its system/init stream event, and Open Design already parses that value. The connection-test sink discarded the status event, however, so the response preserved only the requested slot (opus or default) and the UI could not show what the alias resolved to.

This addresses the resolved-model transparency portion of #6180. The stale Claude fallback catalog is intentionally not changed here because #6095 already refreshes that list and includes Fable 5/current-generation coverage.

What users will see

A successful Local CLI connection test now appends the concrete model reported by the agent when it differs from the selected alias/default slot. For example:

Claude Code replied in 42 ms — 'ok' Model: claude-opus-5

Exact pinned selections are not repeated when the reported model equals the selected model.

Surface area

• UI — the existing Settings → Local CLI test-result message shows the resolved model
• Keyboard shortcut — new or changed
• CLI / env var — new od subcommand or flag, new tools-dev / tools-pack / tools-pr flag, or new OD_* env var
• API / contract — adds the optional, backwards-compatible ConnectionTestResponse.resolvedModel field
• Extension point — new entry under skills/, design-systems/, design-templates/, or craft/, or change to the skills protocol
• i18n keys — no new key; the message reuses the existing localized settings.model label
• New top-level dependency
• Default behavior change — successful alias/default tests show one additional model detail
• None

CLI parity

This does not add a new connection-test capability or endpoint; it preserves metadata in an existing Settings-only test flow. There is currently no od connection-test command to extend. Adding a new CLI command would be a separate user-facing capability and outside this focused bug fix. Any future CLI consumer of /api/test/connection will receive the same optional resolvedModel field from the shared contract.

Screenshots

The visible change is a single appended detail in the existing Local CLI test status row:

Before: Claude Code replied in 42 ms — 'ok'
After:  Claude Code replied in 42 ms — 'ok' Model: claude-opus-5

The rendered behavior is covered by apps/web/tests/components/SettingsDialog.execution.test.tsx. This draft does not include an uploaded screenshot yet.

Bug fix verification

• Daemon red spec: apps/daemon/tests/connection-test.test.ts — reports the concrete model resolved from a Claude alias
• UI red spec: apps/web/tests/components/SettingsDialog.execution.test.tsx — shows the concrete model reported by a Local CLI connection test
• Red on main, green on this branch? Yes. On main, the daemon result lacks resolvedModel, and Settings omits the model from the success message. Both focused specs pass after the fix.

Validation

Passed:

• pnpm guard
• pnpm typecheck (full workspace)
• pnpm --filter @open-design/contracts typecheck
• pnpm --filter @open-design/daemon typecheck
• pnpm --filter @open-design/web typecheck
• Focused daemon regression: 1 passed
• Focused web regression: 1 passed
• Full web suite: 441 files passed; 4,866 tests passed, 7 skipped

Full daemon suite result on this machine:

• 480 files passed; 6,098 tests passed
• 4 files / 12 tests failed in unrelated environment-sensitive areas: AMR session-resume integration (8), Langfuse/Vela endpoint selection (2), and xAI no-credential expectations (2)
• The two Langfuse failures are the same main-baseline failures already documented on fix(daemon): refresh Claude Code fallback model list to the current generation #6095. The AMR/xAI failures do not import or exercise the changed contract, Claude connection-test sink, or Settings result rendering. The directly affected connection-test regression is green.

Implementation

• Capture the existing Claude status / initializing model in the connection-test sink.
• Preserve both meanings in the response: model remains the requested alias/default slot; resolvedModel contains the concrete model reported by the CLI.
• Render the concrete model only for successful Local CLI tests and avoid duplicate output for exact pinned IDs.
• Keep the shared contract additive and optional for backwards compatibility.